[Automated] Sync main after 1.2.0 release#28
Conversation
📝 WalkthroughWalkthroughRelease preparation changes that convert SNAPSHOT dependencies to stable 1.2.0 versions while bumping the project version to 1.2.1-SNAPSHOT for continued development. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
ballerina/Ballerina.toml (1)
4-4:⚠️ Potential issue | 🔴 CriticalRegenerate TOML files from templates using the build system.
The package version and native artifact references in
ballerina/Ballerina.tomlare stale. Sincegradle.propertieswas bumped to1.2.1-SNAPSHOT, the TOML files must be regenerated via theupdateTomlFilesGradle task to reflect this change. The template substitution will produce:
- Line 4:
version = "1.2.1"(stripped SNAPSHOT)- Lines 18-20: Native artifact paths with
1.2.1-SNAPSHOTto match the native build outputRunning the build will regenerate these files correctly; manually editing them to hardcoded SNAPSHOT versions is not the intended pattern for this project, as these files are generated from
build-config/resources/Ballerina.tomltemplates.Also applies to: 18-20
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@ballerina/Ballerina.toml` at line 4, The Ballerina.toml file is stale — do not edit it manually; run the Gradle task that regenerates TOML templates (updateTomlFiles) so the template in build-config/resources/Ballerina.toml substitutes the new version and native artifact paths; this will change the version line from "1.2.0" to "1.2.1" (stripping -SNAPSHOT) and update the native artifact references (lines around 18–20) to include "1.2.1-SNAPSHOT" as produced by the build output.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Outside diff comments:
In `@ballerina/Ballerina.toml`:
- Line 4: The Ballerina.toml file is stale — do not edit it manually; run the
Gradle task that regenerates TOML templates (updateTomlFiles) so the template in
build-config/resources/Ballerina.toml substitutes the new version and native
artifact paths; this will change the version line from "1.2.0" to "1.2.1"
(stripping -SNAPSHOT) and update the native artifact references (lines around
18–20) to include "1.2.1-SNAPSHOT" as produced by the build output.
Codecov Report✅ All modified and coverable lines are covered by tests. ❌ Your project status has failed because the head coverage (76.56%) is below the target coverage (80.00%). You can increase the head coverage or adjust the target coverage. Additional details and impacted files@@ Coverage Diff @@
## main #28 +/- ##
=========================================
Coverage 76.56% 76.56%
Complexity 224 224
=========================================
Files 30 30
Lines 1084 1084
Branches 170 170
=========================================
Hits 830 830
Misses 176 176
Partials 78 78 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
2 participants
Sync main after 1.2.0 release
Summary
This pull request syncs the main branch following the completion of the 1.2.0 release. The changes consist of version updates across configuration files to reflect the finalized release build.
Changes
Build Configuration Updates:
ballerina/Ballerina.tomlto reference the finalized 1.2.0 release artifacts for the io.ballerina.lib.cdc dependency, replacing snapshot versions with stable release versionsballerina/CompilerPlugin.tomlto reference the finalized 1.2.0 release compiler plugin artifactgradle.propertiesto version 1.2.1-SNAPSHOT to prepare for the next development cycleThese changes finalize the transition from the 1.2.0 release branch to the main development line with updated artifact references and incremented version numbers for ongoing development.